fix: add explicit permissions to GitHub Actions workflows#414
Merged
Conversation
InfoSec is changing GITHUB_TOKEN default permissions from read/write to read-only on July 15th. Adding explicit permissions blocks to all workflows that require write access.
Contributor
✅MegaLinter analysis: Success
Notices📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining See detailed reports in MegaLinter artifacts MegaLinter is graciously provided by OX Security |
JoshMock
approved these changes
Jun 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
InfoSec is changing GITHUB_TOKEN default permissions from read/write to read-only on July 15th. This PR adds explicit permissions blocks to workflows that require write access.
Changes
auto-pr.ymlcontents: write,pull-requests: write,issues: read— delegates to reusable workflow that creates PRscodeql.ymlpermissions: {}at top level — job-levelsecurity-events: writealready present, top-level deny-all is best practicedocs-preview-cleanup.ymlpermissions: {}at top level — job-level permissions already scoped correctlyregenerate-notice.ymlpermissions: {}at top level — job-levelcontents: writealready present forgit pushresolve-conflicts.ymlcontents: write,pull-requests: write,issues: read— delegates to reusable workflow that resolves backport conflictsReferences